feat(pr): add resumable sequential merge batches - #2761
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_abeb2a10-ee34-4ebc-9302-3ac53a8102d3) |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 49bcab61f3
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex resolve actionable Codex review findings for this pull request and current head using the repository instructions. This is the pull request's single automatic repair pass: do not perform a fresh review, create new standalone findings, or request another review. Work only the existing unresolved Codex threads on the current head. The only repository destination is BigSimmo/Database, and the only branch destination is the pull request head branch codex/chat-pr-batch-runner-1076 at starting commit 49bcab6; never publish fixes to a detached or synthetic work branch and never create a stacked pull request. Use the authenticated GitHub connector to commit each approved fix to BigSimmo/Database:codex/chat-pr-batch-runner-1076, then verify that the pull request head contains the published commit before reporting success. Always fix P0 and P1 findings. For P2 and lower findings, fix only clear, scoped, low-risk issues; otherwise disposition them with a concise reason. For a fixed thread, reply with as the first line and as the second line. For a no-code disposition, use followed by . These result markers authorize the workflow to close that exact thread only after it verifies a fixed commit is the pull request head; a local-only commit is not a fix. If publication or verification fails, do not use either result marker, do not claim success, and leave the thread open with the blocker. If human input or new authorization is required, do the same. Finish only after every actionable thread is fixed or dispositioned and closed, or explicitly left open for a human decision. Do not update the branch from main, address unrelated reviews, broaden scope, or create more than one scoped fix commit. Do not use external APIs, paid services, credentials, dependency changes, or broad refactors unless explicitly authorized. Add targeted tests where behavior changes and run the narrowest relevant validation. |
|
Codex Review: Didn't find any major issues. Nice work! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
CI triageCI failed on this PR. Automated classification of the 2 failed job(s):
Compared with main CI run #16436 (failure). Classification is evidence routing, not permission to ignore a failure. Exact quarantined Playwright identities remain governed by the flake ledger. |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_d52f6e7e-e963-47d3-bdf3-14f52c665297) |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_ac9acc3e-cd6f-489c-b36c-b01c29dd3340) |
1 participant
Summary
Clear PRsrepository shortcut and activation guide. Preserve migration, clinical/RAG, provider, and controller-policy exclusions.Verification
Prior implementation checks (not repeated for this publication):
npm run test -- tests/pr-batch-runner.test.ts tests/pr-batch-github.test.ts tests/codex-run-pr-operator-workflow.test.ts tests/codex-autofix-workflow.test.ts— 124 tests passed.npm run typecheck— passed.lint:changed:internalon changed scripts and tests with--max-warnings 0— passed.npm run check:github-actionsandnpm run check:codex-autofix-workflow— passed.node scripts/update-docs-inventory.mjs --checkandgit diff --check— passed.verify:pr-localsuite; focused controller/operator tests and workflow guards cover the changed contracts. Hosted checks remain authoritative before merge.Risk and rollout
PR_BATCH_ENABLEDabsent/false or pause a batch. Pausing does not revoke an already-issued merge request; never silently disable user-owned auto-merge.Clinical Governance Preflight
Not applicable to application behavior: no ingestion, clinical output, document access, privacy, source rendering, or production environment configuration changes. The batch eligibility checks preserve existing governance and migration restrictions.
Notes
Note
High Risk
When activated, the batch path authorizes GitHub writes, protected merges, repair API use, and Railway deployments; mistakes in ownership, signing, or publication could affect production merge flow.
Overview
Introduces a disabled-by-default sequential PR batch runner that snapshots eligible open PRs, journals work on an HMAC-authenticated
codex/pr-batch-statebranch, and drives one PR at a time through sync, bounded Codex repairs, review replies/resolutions, and protected merge requests (with optional RAG canary proof).Codex Run PR and review auto-fix now share a
pr-batch-mutationconcurrency group and yield when a PR is batch-reserved. The operator gains optionalbatch_id/batch_operationinputs, can leave a pending base merge for batch repairs (compare tree vs. head for publication), requiresprogress_outcomein sealed results, and journals candidates plus batch-side mutations throughpr-batch-worker.mjs.Adds the
Clear PRsagent shortcut anddocs/pr-batch-runner.mdactivation guide, extends workflow/policy guards and CI tests (pr-batch-*.test.ts), and ignores.codex-run-pr/in Prettier so sealed digests stay stable.Reviewed by Cursor Bugbot for commit 92c0b81. Configure here.